Please address the comments from this code review:

## Overall Comments
- In `call_tool_with_reconnect`, the line that actually invokes the tool (`self.session.call_tool(...)`) appears to have been removed, so `return await (` will raise a syntax/runtime error; you likely want `return await self.session.call_tool(...)` as before with the new retry logic around it.
- The new manual retry loop removes the previous exponential backoff and detailed tenacity logging; if repeated reconnects are expected in some deployments, consider adding a small delay or backoff between attempts and ensuring failures are logged in a way that preserves the previous observability.

## Individual Comments

### Comment 1
<location path="astrbot/core/agent/mcp_client.py" line_range="666-669" />
<code_context>

             try:
-                return await self.session.call_tool(
+                return await (
                     name=tool_name,
                     arguments=arguments,
                     read_timeout_seconds=read_timeout_seconds,
                 )
-            except anyio.ClosedResourceError:
</code_context>
<issue_to_address>
**issue (bug_risk):** The call to `call_tool` is missing the target coroutine (`self.session.call_tool`), making this invalid and likely a runtime error.

Previously this block correctly called `self.session.call_tool(...)`, but now it just awaits a parenthesized list of keyword arguments, which is invalid syntax and will fail at runtime. Please restore the explicit call, e.g.

```python
return await self.session.call_tool(
    name=tool_name,
    arguments=arguments,
    read_timeout_seconds=read_timeout_seconds,
)
```
</issue_to_address>

### Comment 2
<location path="astrbot/core/agent/mcp_client.py" line_range="671" />
<code_context>
                     read_timeout_seconds=read_timeout_seconds,
                 )
-            except anyio.ClosedResourceError:
+            except BaseException as e:
+                last_exc = e
+
+                if not _is_connection_error(e):
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Catching `BaseException` may swallow cancellations and other critical signals; consider restricting to `Exception`.

This will also catch `asyncio.CancelledError`, `KeyboardInterrupt`, and `SystemExit`. In async code that can break task cancellation and shutdown, especially if this layer retries or suppresses the error. Limiting the handler to `Exception` and letting cancellations/termination signals propagate is safer:

```python
except Exception as e:
    ...
```

```suggestion
            except Exception as e:
```
</issue_to_address>

### Comment 3
<location path="astrbot/core/agent/mcp_client.py" line_range="125-133" />
<code_context>
+)
+
+# Keywords in exception messages that indicate a transport/connection problem.
+_CONNECTION_ERROR_KEYWORDS = (
+    "session terminated",
+    "terminated",
+    "closed resource",
+    "broken resource",
</code_context>
<issue_to_address>
**suggestion (bug_risk):** The generic keyword "terminated" may falsely classify unrelated errors as connection issues.

This broad substring match risks treating unrelated lifecycle or business errors as transport failures, triggering unnecessary reconnects. Consider restricting matching to more specific phrases (e.g., variants of the existing "session terminated") or otherwise tightening the condition so it only captures genuine connection/transport errors.

```suggestion
# Keywords in exception messages that indicate a transport/connection problem.
# Note: avoid overly generic substrings (e.g. just "terminated") to prevent
# misclassifying unrelated lifecycle or business errors as connection issues.
_CONNECTION_ERROR_KEYWORDS = (
    "session terminated",
    "session was terminated",
    "closed resource",
    "broken resource",
    "connection closed",
    "connection reset",
)
```
</issue_to_address>